MP CONNECT programs might become unresponsive when data is piped between tasks using the SASESOCK engine and when explicit ports are used. The program can behave differently on different machines, with different versions of SAS^® software, and with different time-out values. An example of the code that causes the problem is included on the Full Code tab.

To work around this problem, use service names for open ports instead of direct port numbers.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

options sascmd="!sascmd";
signon task1;
signon task2;

rsubmit task1 cwait=no;
libname pipe1 sasesock ":8001" timeout=500;
data pipe1.test;
  do i=1 to 10000000;
    x1=ranuni(2992029);
    x2=ranuni(2994029);
    output;
  end;
run;
endrsubmit;

rsubmit task2 cwait=no;
libname pipe1 sasesock ":8001" timeout=500;
proc means data=pipe1.test;
  var x1 x2;
run;
endrsubmit;

listtask _all_; 

waitfor _all_ task1 task2; 
rget task1; 
rget task2; 
signoff task1; 
signoff task2; 

A fix for this issue for SAS/CONNECT 9.21_M2 is available at: